Multi-function electronic device-enabled transmit controller

ABSTRACT

In an embodiment, a transmit controller capable of automatic configuration is provided. In another embodiment, an auxiliary user interface device for automatically configuring a transmit controller is provided. In another embodiment, an auxiliary user interface device for transmitting operational parameter settings is provided. In another embodiment, an auxiliary user interface device for receiving operational parameter settings is provided. In another embodiment, an auxiliary user interface device for updating an application program of a receiving device is provided.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims the benefit of thefiling date of, co-pending international application no.PCT/US2012/062613 entitled MULTI-FUNCTION ELECTRONIC DEVICE-ENABLEDTRANSMIT CONTROLLER, filed Oct. 30, 2012, which claims the benefit ofU.S. provisional patent application Ser. No. 61/553,863 entitledMULTI-FUNCTION ELECTRONIC DEVICE-ENABLED TRANSMIT CONTROLLER, filed Oct.31, 2011. The entire contents of both applications are incorporatedherein by reference for all purposes.

TECHNICAL FIELD

This application relates to model vehicle transmit controllers and, moreparticularly, to user interfaces for model vehicle transmit controllers.

BACKGROUND

A radio control model vehicle, such as a radio control automobile, boat,or airplane, may be controlled remotely by a transmit controller. Atransmit controller is often an exclusively hardware device with anexclusively hardware built-in user interface. In a transmit controller,all user input may be received through mechanical hardware componentssuch as knobs, dials, wheels, and switches. Output to the user might beprovided solely through labeled positions of the hardware components anda few LEDs.

The built-in user interface of a transmit controller may be separatedinto two parts: a control user interface and a parameter user interface.The control user interface directly controls the movement of the modelvehicle. For example, in a typical model automobile, the control userinterface includes a steering wheel and a throttle trigger. When theuser turns the steering wheel, the wheels of the vehicle may moveaccordingly. When the user displaces the trigger toward the grip, thevehicle may accelerate, and when the user displaces the trigger awayfrom the grip, the vehicle may brake.

The parameter user interface allows a user to set operational parameterswhich indirectly control the operation of the vehicle. These operationalparameters may be factory-set or user-specified. Some parameters may bemandatory parameters which must be set correctly to properly control thevehicle. Other parameters may be permissive parameters which may be setas a matter of preference. An example of a mandatory parameter is servoreversing, which determines whether the left-right steering of the usershould be reversed to compensate for vehicles with reversed steeringservos. Examples of permissive parameters include model vehicleacceleration, steering, and braking configurations.

The operational parameters may be stored in a memory of the transmitcontroller. The parameters may affect how the transmit controllertranslates input from the control user interface into output to themodel vehicle. The transmit controller can be said to “determine” anoutput signal to the model vehicle based on the parameters and the inputto the control user interface. In other words, the parameters maydetermine whether or not the transmit controller modifies a controlinstruction from the control user interface and, if the controlinstruction is modified, the parameters may determine how the controlinstruction is modified. A collection of parameter settings may bereferred to as a “profile.”

In general, the functions of existing transmit controllers areinflexible. A user can do little beyond setting operational parametersusing the parameter user interface and controlling the vehicle using thecontrol user interface. In particular, it is difficult for one user toshare a profile with another user. It is also difficult for a user toconfigure a transmit controller to communicate with telemetry sensors,and a transmit controller is typically unable to record data fromtelemetry sensors.

Adding additional electronic components to a conventional transmitcontroller may improve its functionality, but may also add significantlyto the cost of the transmit controller. In addition, powering additionalcomponents may also significantly reduce the transmit controller'sbattery life. Thus, a need exists for a transmit controller which offersadditional functionality without extensive additional components.

SUMMARY

In an embodiment, a transmit controller capable of automaticconfiguration is provided. The transmit controller has a memory havingone or more operational parameters, a control user interface forcontrolling a model vehicle, an auxiliary user interface connector forconnecting to an auxiliary user interface device, and a transmitcontroller processor. The transmit controller processor has aconfiguration to receive a vehicle identifier from a model vehiclereceiver, transmit the vehicle identifier to the auxiliary userinterface device, receive one or more operational parameter settingsfrom the auxiliary user interface device in response, and change the oneor more operational parameters to the one or more operational parametersettings. The configuration is further to receive a control instructionfrom the control user interface, determine an output signal based on thecontrol instruction and the one or more operational parameters, andtransmit the output signal to the model vehicle.

In another embodiment, an auxiliary user interface device forautomatically configuring a transmit controller is provided. Theauxiliary user interface device has a configuration to receive a vehicleidentifier from a transmit controller, identify one or more operationalparameter settings associated with the vehicle identifier in a vehicledatabase, and transmit the one or more operational parameter settings tothe transmit controller.

In another embodiment, an auxiliary user interface device fortransmitting operational parameter settings is provided. The auxiliaryuser interface device comprises a configuration to store one or moreoperational parameter settings, transmit the one or more operationalparameter settings to a network address at a server, and send anelectronic mail message comprising the network address.

In another embodiment, an auxiliary user interface device for receivingoperational parameter settings is provided. The auxiliary user interfacedevice comprising a configuration to receive an electronic mail messagecomprising the network address of one or more operational parametersettings, retrieve the one or more operational parameter settings fromthe network address, and store the one or more operational parametersettings.

In another embodiment, an auxiliary user interface device for updatingan application program of a receiving device is provided. The auxiliaryuser interface has a configuration to receive an updated applicationprogram from a data network and transmit the updated application programto a model vehicle transmit controller.

DESCRIPTION OF DRAWINGS

For a more complete understanding of the present invention and theadvantages thereof, reference is now made to the following DetailedDescription taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 depicts a combination of an MFED, transmit controller, receiver,and telemetry sensor in accordance with an exemplary embodiment of thepresent invention;

FIG. 2 depicts an exemplary dashboard user interface elements offered byan MFED;

FIG. 3 depicts a graph showing the effect of two exemplary maximum powerparameter settings;

FIG. 4 depicts an exemplary maximum power parameter slider that may bedisplayed by a touch screen of an MFED;

FIG. 5 depicts an exemplary method for setting a maximum powerparameter;

FIG. 6 depicts an exemplary method for automatically configuring atransmit controller and an MFED to operate with a particular model andversion of model vehicle;

FIG. 7A depicts an exemplary method for sending a profile or partialprofile;

FIG. 7B depicts an exemplary method for receiving a profile or partialprofile;

FIG. 8 depicts an exemplary method for automatic configuration of atelemetry sensor;

FIG. 9 depicts an exemplary method for creating a video of a virtualdashboard;

FIG. 10 depicts an exemplary method for providing an instant replayfeature;

FIG. 11 depicts an exemplary method an MFED may perform to try and retrythe sending of software to a receiving device;

FIG. 12 depicts an exemplary method a receiving device may perform todownload software from an MFED;

FIG. 13A-13C depict an exemplary method for configuring user interfaceelements shown in a dashboard for an MFED;

FIG. 14 depicts an exemplary method for setting a maximum powerparameter for an MFED;

FIG. 15 depicts an exemplary diagram of messages sent between an MFED, atransmit controller, a receiver, and a telemetry sensor or expander; and

FIG. 16A-16AH depict screen captures of selected portions of theexecution of an exemplary MFED application.

DETAILED DESCRIPTION

In the following discussion, numerous specific details are set forth toprovide a thorough explanation. However, such specific details are notessential. In other instances, well-known elements have been illustratedin schematic or block diagram form. Additionally, for the most part,specific details within the understanding of persons of ordinary skillin the relevant art have been omitted.

A transmit controller may have the capability to communicate with amulti-function electronic device (MFED). The transmit controller mayfunction alone, without the MFED, and provide a basic, built-innon-graphical parameter user interface. To provide an expanded parameteruser interface, a MFED may be connected to the transmit controller andserve as an auxiliary user interface. The MFED may be attached to thetransmit controller where the user may interact with the MFED whileusing the transmit controller.

MFEDs may be devices such as mobile smart phones, personal digitalassistants, and digital music players. These devices are commonlyavailable and commonly programmable. By using a MFED, the transmitcontroller may present a graphical user interface with only the hardwarenecessary to communicate with the MFED, rather than a built-in LCDdisplay, touch screen, audio output, and so on. A user who owns atransmit controller and a MFED may save the expense of additionalhardware components in the transmit controller by utilizing the hardwarecomponents available in the MFED.

Many MFEDs are capable of providing rich graphical user interfacescomparable to the graphical user interfaces of personal computers. Forinput, these devices may have a touch screen or keyboard. These devicesmay have high-resolution displays with the same range of colors as apersonal computer monitor. These devices are often usable as musicplayers and consequently may be capable of producing high-quality audiooutput. Some devices may have vibration capabilities.

Many MFEDs also have an external interface for communication with anexternal device. The external device is often a personal computer.Through the external interface, the MFED may communicate with thepersonal computer and vice versa. A MFED may function as an auxiliaryuser interface for a transmit controller. In an exemplary embodiment, aMFED communicates with a model vehicle transmit controller using theexternal interface, allowing the MFED to function as an auxiliary userinterface for a transmit controller.

With reference to FIG. 1, depicted is a combination 100 of a MFED 102,transmit controller 104, and receiver 106 in accordance with anexemplary embodiment. The transmit controller 104 and receiver 106 maybe in radio communication through radio link 108 as is known in the art.Despite their names, both transmit controller 104 and receiver 106 maybe capable of both transmitting and receiving radio communications.Thus, transmit controller 104 and receiver 106 may each be called a“transceiver,” but to distinguish between the two devices the terms“transmit controller” and “receiver” will be used herein.

The MFED 102 may be a smart phone or digital music player. ExemplaryMFEDs are the iPhone and iPod Touch produced by Apple Inc. Both of theseexemplary MFEDs may accept user input via a touch screen. MFED 102 maybe connected to transmit controller 104 through external interface 102Aof MFED 102. External interface 102A may be a conventional hardwareinterface of MFED 102, such as the connection used by MFED 102 tocommunicate with a personal computer.

Transmit controller 104 may have a dock for storing MFED 102, so thatthe user may more easily concurrently operate both devices. A typicalMFED 102 may be physically smaller in volume, or at least notsubstantially larger in volume, than a typical transmit controller 104.The reason is that a user may be expected to operate MFED 102 whilesimultaneously controlling a vehicle with transmit controller 104. Iftransmit controller 104 is designed to be held with both hands, asubstantially larger MFED 102 may be difficult for the user to workwith.

MFED 102 may execute a software application for communication withtransmit controller 104. The software application may be provided toMFED 102 through an Internet download. Internet download is a commonsoftware application delivery method for many MFEDs.

Transmit controller 104 may have processor 104A. Processor 104A maydetermine what output signal is transmitted to receiver 106 over radiolink 108. The output signal may be determined from user input fromcontrol user interface 104B and one or more parameters stored in memory104C. Control user interface 104B may be components of transmitcontroller 104 which permit a user to directly control the operations ofa model vehicle. These components may include a steering wheel andthrottle trigger. Once processor 104A determines the output signal thatshould be transmitted, it may send the signal through a radio frequencymodule.

Transmit controller 104 may connect to external interface 102A of MFED102 through auxiliary user interface connector 104E. The connectionbetween external interface 102A and auxiliary user interface connector104E may be wired or wireless, and a wired connection may be throughdirect contact or through a cable between the two devices. In someembodiments, auxiliary user interface connector 104E may include acable, with one end of the cable permanently attached to transmitcontroller 104.

A wireless connection between external interface 102A and auxiliary userinterface connector 104E may be a Bluetooth connection. The wirelessconnection between external interface 102A and auxiliary user interfaceconnector 104E may also be a wireless local area network connectionusing a standard such as IEEE 802.11, also known as Wi-Fi. Externalinterface 102A and auxiliary user interface connector 104E may includeBluetooth or 802.11 transceivers. MFED 102 may be a mobile smart phone,and many mobile smart phones include Bluetooth and 802.11 transceivers.Auxiliary user interface 104E may utilize a Bluetooth or 802.11transceiver built into transmit controller 104 or an external donglewith a Bluetooth or 802.11 transceiver.

One advantage of using a wireless connection between external interface102A and auxiliary user interface connector 104E is that a singletransmit controller 104 may easily support different types of MFEDs 102.Different MFED manufacturers may use different physical connections fortheir MFEDs. Accordingly, transmit controller 104 may be require aseparate external interface 102A for each type of MFED. In contrast, awireless standard such as Bluetooth or 802.11 may typically be supportedby a variety of devices.

Another advantage of using a wireless connection between externalinterface 102A and auxiliary user interface connector 104E is that thewireless connection permits MFED 102 to be separated from transmitcontroller 104. A user's pit man, for example, could use MFED 102 whilethe user continues to operate the vehicle with transmit controller 104.Further, if a wireless local area network connection such as IEEE 802.11is used, multiple MFEDs 102 may be in communication with a singletransmit controller 104 at the same time. Therefore, a user and theuser's pit man may each have a functioning MFED 102 while the user iscontrolling the vehicle with transmit controller 104.

When MFED 102 is not connected, the user may modify the parameters inmemory 104C through parameter user interface 104D. Parameter interface104D may allow the user to modify basic parameters such as servoreversing, steering sensitivity, and throttle sensitivity. These basicparameters may be sufficient for the user to operate the model vehicle,but may be limited by the input and output capabilities of parameterinterface 104D.

When the user connects MFED 102 to auxiliary user interface connector104E, MFED 102 may provide the user with a graphical user interfacepermitting the user to gain access to additional parameters andadditional feedback. MFED 102 may also offer a graphical display ofparameter values as they are set through parameter interface 104D.

Referring to FIG. 2, depicted is an exemplary “dashboard” 200 of userinterface elements that an MFED may offer a user. The dashboardgraphically displays a variety of data for the user obtained fromtelemetry sensors installed in the model vehicle, including enginetemperature, motor RPM, vehicle speed, and battery voltage. Dashboard200 also displays the vehicle's top speed for this session, which theMFED tracks from the vehicle speed telemetry data. The user mayconfigure the user interface elements shown in a dashboard and theirarrangement to the user's preference, as shown and described more fullyin FIG. 13A-13C.

Referring to FIG. 1, the configuration of the dashboard may be stored ina profile as a set of parameters which are used only when MFED 102 isconnected. The graphical user interface may also provide the user withaccess to the same parameters and feedback available through transmitcontroller 104 alone. Parameter user interface 104D may becomeinoperable when MFED 102 is connected.

To display a parameter, auxiliary user interface device 102 may requestthe parameter from processor 104A. In response to the request, parameter104A may transmit the parameter from memory 104C to MFED 102.

When the user chooses to modify a parameter using MFED 102, MFED 102transmits a parameter instruction to transmit controller 104. Theparameter instruction instructs processor 104A to modify the parameterin memory 104C according to the user's input.

MFED 102 may transmit signals to and receive signals from the vehiclethrough transmit controller 104. Through the graphical user interfaceprovided by MFED 102, the user may set the various parameters stored inmemory 104C. The user may set be able to set the parameters in memory104C while operating a model vehicle, while not operating a modelvehicle, or both.

MFED 102 may store a list of profiles for the user to select from. Thegraphical user interface of MFED 102 offers a convenient way to view andedit these profiles. When the user selects a profile, MFED 102 mayinstruct transmit controller 104 to store parameters for that profile inmemory 104C. MFED 102 may also configure itself according to theselected profile, such as displaying a dashboard specified by parametersin the selected profile.

An exemplary parameter which may be set using the MFED 102 is a reducedmaximum power parameter. The maximum power parameter may be expressed asa percentage of “absolute maximum” power1 the receiver can cause to besupplied to the motor of the model vehicle. Transmit controller 104 mayinterpret all acceleration specified by control user interface 104B asrelative to the maximum power parameter. The maximum power parameterallows a user to reduce the amount of power which can be supplied to themotor, which in turn allows an inexperienced user to more easilymaintain control of the model vehicle. The maximum power parameter maybe set in real time while the vehicle is stationary or while the vehicleis in motion, including while the user moves the throttle trigger. ¹Power is commonly supplied to the motor of a model vehicle as a squarewave, with the duty cycle of the square wave controlling theacceleration of the vehicle. Technically, in such cases the accelerationof the model vehicle varies with the average amount of power supplied tothe motor. For simplicity this discussion will consistently refer to the“amount” of power supplied, with the “amount” of power understood tomean the average amount of power in such cases.

For example, suppose acceleration of the model vehicle is controlled bya throttle trigger on control user interface 104B, and the maximum powerparameter is set to 20%. The user may move the throttle trigger to amaximum throttle position, an input which instructs transmit controller104 to supply 100% of the maximum power parameter to the motor. Transmitcontroller 104 would cause receiver 106 to apply 100% of the 20% maximumpower parameter to the motor, which is 20% of the absolute maximumpower. If the input was a half throttle position instructing transmitcontroller 104 to supply 50% of the maximum power parameter to themotor, transmit controller 104 would instruct receiver 106 to 10% ofabsolute maximum power to the motor. If the input was a quarter throttleposition instructing transmit controller 104 to supply 25% of themaximum power parameter to the motor, transmit controller 104 wouldinstruct receiver 106 to supply 5% of the absolute maximum power to themotor, and so on.

Referring to FIG. 3, depicted is a graph 300 showing the effect of twoexemplary maximum power parameter settings. Curves 304A and 304B showthe power supplied to the motor at throttle positions between a neutralthrottle position and a maximum throttle position. For curve 304A, themaximum power parameter is set to 100%. Curve 304A gradually increasesfrom no power supplied to the motor at the neutral throttle position tothe absolute maximum power supplied to the motor at the maximum throttleposition. For curve 304B, the maximum power parameter is set to 50%. Foreach throttle position, the power supplied to the motor in curve 304B is50% of the power supplied to the motor in curve 304A. At the maximumthrottle position, 50% of the absolute maximum power is supplied to themotor in curve 304B.

MFED 102 provides a convenient graphical interface for adjusting themaximum power parameter. Referring to FIG. 4, depicted is an exemplarymaximum power parameter display 400 that may be displayed by a touchscreen of the MFED. In FIG. 4, the maximum power parameter is describedas the “throttle level.” Display 400 shows the current maximum powerparameter both graphically and numerically. Display 400 permits a userto easily see the maximum power parameter over a wide range of possiblevalues, such as any whole percentage between 5% and 100%.

Display 400 works in conjunction with a knob on the transmit controller.The user adjusts the maximum power parameter using the knob, and themaximum power parameter is shown in display 400. The use of display 400in setting the maximum power parameter is shown and described more fullyin FIG. 14. In an alternate embodiment, a user could use a touch screenof the MFED to both adjust and see the maximum power parameter.

Referring to FIG. 5, depicted is an exemplary method 500 for setting themaximum power parameter. At 502, the MFED provides the user with agraphical interface, such as the slider depicted in FIG. 5, for settingthe maximum power parameter. At 504, the MFED receives the user'ssetting through the slider. At 506, the MFED transmits the setting tothe processor of the transmit controller. At 508, the processor of thetransmit controller stores the maximum power parameter in the memory ofthe transmit controller. The transmit controller processor can thenretrieve the maximum power parameter from the memory when interpretinginput from the control user interface. As discussed above, theacceleration of the model vehicle specified by the control userinterface may be relative to the maximum power parameter.

Referring to FIG. 1, receiver 106 may have a receiver ID 112 on anelectronic security chip. Receiver ID 112 may identify receiver 106 toMFED 102. First, receiver ID 112 may have a globally unique ID (GUID)112A, which uniquely identifies the particular receiver 106 from otherreceivers. Second, receiver ID 112 may have a model/version ID 112Bwhich identifies the vehicle receiver 106 is installed in.

Model/version ID 112B may identify the model vehicle in one of two ways.First, model/version ID 112B may identify the model and version of themodel vehicle because model/version ID 112 is unique to that model andversion of model vehicle. Second, model/version ID 112 may identify themodel vehicle as a model vehicle which has had receiver 106 installedafter the vehicle was manufactured. This could be because receiver 106replaced a previous receiver for the model vehicle.

MFED 102 may store a model/version database 116 having configurationdata for a variety of vehicle models and versions. Exemplaryconfiguration data in model/version database 116 may include:

-   -   How the user interface of MFED 102 should be configured for the        model and version;    -   Vehicle specific graphics for the user interface of MFED 102;    -   Vehicle characteristics necessary to calculate the vehicle        speed, such as gear ratio and tire diameter;    -   The type of battery or batteries in the model and version, and        the associated battery voltages for full, empty, etc.;    -   Safe operating temperatures for components of the vehicle,        including the engines, motors, and batteries;    -   The thermistor correlation curve for the thermistor of the        vehicle, used in compensation necessary for accurate (within        3-4° Fahrenheit) measurement at high temperatures;    -   The operating and control characteristics of smart modules and        sensors connected to the vehicle;    -   Factory settings for permissive operational parameters, such as        steering expo, brake percentage, etc.; and    -   Factory settings for mandatory operational parameters, such as        end points and servo reversing.

Referring to FIG. 6, depicted is an exemplary method 600 forautomatically configuring a transmit controller and an MFED to operatewith a particular model and version of model vehicle. At 602, when aradio link is established between a transmit controller having an MFEDand a receiver having a model/version ID, the receiver may provide themodel/version ID to the MFED through the radio link and the transmitcontroller. At 604, the MFED may identify the model vehicle model andversion corresponding to the model/version ID. If the model/version IDis for a receiver installed after the manufacture of a model vehicle,the MFED may prompt the user to select the model and version.

In either case, the MFED may find configuration data for the identifiedmodel and version in the model/version database. The MFED may configureitself to function as specified by the configuration data. For example,the MFED may present a dashboard of telemetry data specific to theparticular model and version of the model vehicle. The MFED may alsoconfigure parameters stored in the transmit controller memory. At 606,the MFED may provide parameter settings from the configuration data tothe transmit controller processor. At 608, the transmit controllerprocessor may store those parameter settings in the transmit controllermemory.

In addition to automatic configuration using the model/version database,an MFED may offer a model history feature. The model history feature mayprovide a “warehousing” of information related to each model vehiclethat has been controlled by a transmit controller connected to the MFED.Essentially, the model history feature may separately record the entiremodel setup configuration for each model vehicle. When the transmitcontroller reconnects to one of these model vehicles, the MFED mayrecognize the vehicle by the GUID of its receiver and offer the optionof using the model setup configuration recorded by the model historyfeature. For a user who owns multiple vehicles with customizedconfiguration data, the model history feature may save significant timere-setting the configuration of each vehicle when it is connected.

Receivers installed after the manufacture of a model vehicle may bemoved between vehicles. As described previously, for this type ofreceiver the user may be prompted to select the model and version of aconnected vehicle. In this case, the model history feature may recognizethe vehicle by both the GUID of the receiver and the selected model andversion.

Because MFEDs commonly have network connectivity capabilities, themodel/version database may be remotely updated. Subsequent models andversions may be added to the model/version database, new features forexisting models may be added, and the configurations for existing modelsand versions may be revised. The updates for the model/version databasemay be downloaded by the MFED through an Internet connection.

The network connectivity capabilities of an MFED may also be used topermit transmit controllers to share profiles with one another.Alternately, a user may share a “partial profile,” which is a selectionof less than all of the parameter settings in a profile. Referring toFIG. 7A, depicted is an exemplary method for sending a profile orpartial profile. A sending user may select a profile or partial profileto share from a list of profiles stored in the MFED, or from the memoryof the transmit controller. At 702, the MFED may receive the sendinguser's selection. At 704, the MFED may send the profile or partialprofile to a server. At 706, the MFED may then create an electronic mailmessage containing a hyperlink to the profile or partial profile. Theelectronic mail message may be created in a conventional electronic mailapplication of the MFED. The sending user may edit the message andselect a recipient. At 708, the MFED may send the message to thereceiving user. In addition to sending the message via an Internetconnection, the MFED may send the message via an ad hoc network,including a Bluetooth, Wi-Fi, or cable ad hoc network.

Referring to FIG. 7B, depicted is an exemplary method for receiving aprofile or partial profile. At 710, the receiving user's MFED mayreceive the electronic mail message sent by the sender. At 712, when thereceiving user selects the hyperlink to the profile or partial profile,the receiving user's MFED may recognize the hyperlink as a hyperlink toa profile or partial profile based on the hyperlink URL. At 714, thereceiving user's MFED may then launch an application for operating amodel vehicle. At 716, the application may retrieve the profile from theserver and add the profile to the receiving user's list of profiles. Theapplication may subsequently configure the MFED and the receiving user'stransmit controller to use the retrieved profile.

Referring to FIG. 1, telemetry sensor 110 may communicate with receiver106. Telemetry sensor 110 may be connected to a telemetry connector inthe model vehicle, connected to a telemetry connector in receiver 106,or connected to an expander connected to a telemetry connector. Multipletelemetry sensors may communicate with a single receiver.

Telemetry sensor 110 may capture telemetry data and provide it toreceiver 106. Receiver 106 may transmit the telemetry data to transmitcontroller 104 over radio link 108. The telemetry data may include datasuch as motor temperature, motor RPM, speed, battery voltage, and fuellevel. Transmit controller 104 may provide the telemetry data to MFED102, if it is attached. In an alternative embodiment, telemetry sensor110 and MFED 102 may communicate directly, without passingcommunications through transmit controller 104.

Telemetry data may be provided to the user through built-in componentsof transmit controller 104, but the inclusion of MFED 102 can greatlyimprove the presentation of the telemetry data to the user. For example,in addition to using its graphical display, MFED 102 may providefeedback to the user through its audio and vibration capabilities.

An exemplary parameter which takes advantage of the output capabilitiesof the auxiliary user interface is an accelerometer sensor in the modelvehicle. The accelerometer sensor can be used to detect bumps,collisions, jumps, and landings of the model vehicle. The accelerometersensor can provide the acceleration data to the MFED 102 throughreceiver 106, radio link 108, and transmit controller 104. MFED 102 mayvibrate during periods of sudden changes in acceleration of the modelvehicle, providing additional feedback to the user. Because the feedbackis tactile, the user may receive the feedback even when the user is notlooking at transmit controller 104 or MFED 102.

Telemetry sensor 110 may have a sensor ID 114 on an electronic securitychip. Similar to receiver ID 112, sensor ID 114 may include a globallyunique ID (GUID) 114A, which uniquely identifies the particulartelemetry sensor 110 from other telemetry sensors. Sensor ID 114 mayalso have a type/version ID 114B which identifies the type of datasensed by telemetry sensor 110 and the version of telemetry sensor 110.

Referring to FIG. 8, depicted is an exemplary method 800 for automaticconfiguration of a telemetry sensor. At 802, a receiver may detect atelemetry sensor has been connected. At 804, the receiver may read thesensor ID and transmit the sensor ID to an MFED via a transmitcontroller. The sensor ID allows the telemetry sensor to correctlytransmit data when connected to an arbitrary connector on the receiver,the model vehicle, or an expander. Because any port may be used, a userinstalling the telemetry sensor does not have to identify a compatibleport for installing the telemetry sensor.

At 806, the MFED may determine the type and version of the telemetrysensor from the type/version ID. From the type and version of thesensor, the MFED may determine which data channel data from the sensorshould be directed to. At 808, the MFED may present the user with a listof options for displaying data from the telemetry sensor. For example,for a speed sensor the MFED may present the user with the choice of ananalog or a digital speedometer for a dashboard. The user may select acustom name for the sensor.

FIG. 15 shows a diagram of messages sent between the MFED (labeled“APP”), transmit controller (labeled “Transmitter”), receiver (labeled“Receiver”), and telemetry sensor or expander (labeled “Smart Device”).In addition to telemetry sensors, the MFED may communicate with anexpander to receive telemetry data from the telemetry sensors connectedto the expander.

In addition to displaying telemetry data in a real-time dashboard, anMFED may record telemetry sensor data and create a video of a “virtual”dashboard. Referring to FIG. 9, depicted is an exemplary method forcreating a video of a virtual dashboard. At 902, an MFED may recordtelemetry sensor data for a user-specified period. At 904, the user maythen select a dashboard configuration to display the data. The MFED maycreate a video of the virtual dashboard displaying the recorded data asthe data would have been shown in the virtual dashboard if thatdashboard configuration were in use when the data was recorded. At 906,the video may be published to a public website for public viewing.

When the MFED is not recording telemetry data, the user may experiencean extraordinary event the user would like to review. Referring to FIG.10, depicted is an exemplary method 1000 for providing an “instantreplay” feature. At 1002, the MFED may automatically record a certainamount of past telemetry data when the MFED is not already set to recordtelemetry data. The recorded telemetry data may be stored in a circularbuffer. For example, the MFED may automatically record the last 60seconds of telemetry data. The MFED dashboard may have an “instantreplay” button for the user to press upon experiencing an extraordinaryevent. At 1004, when the user presses the instant replay button, theMFED may save and replay the contents of the circular buffer.

Referring to FIG. 1, MFED 102 may download updated software for devicesMFED 102 communicates with, including transmit controller 104, receiver106, telemetry sensor 110 and any other telemetry sensors, and anyexpander connecting telemetry sensor 110 to receiver 106. MFED 102 mayreceive new software and check what the existing software versions arefor the available devices which can receive updated software (“receivingdevices”). MFED 102 may communicate with a receiving device throughtransmit controller 104, except when transmit controller 104 is itselfthe receiving the device.

Each receiving device may have a memory which may store three programs:a boot loader program, an application program, and a downloader program.The boot loader program may determine which of the other two programs torun. The application program may cause the device to perform itsfunctions other than downloading updated programs. A program may notreplace itself, so a downloader program is used to download a newapplication program. Likewise, an application program is used todownload a new downloader program. The boot loader program may not beupdated.

Referring to FIG. 11, depicted is a process 1100 which an MFED may useto try and retry sending a downloader program or application program toa receiving device. At step 1102, the MFED may make an authorizationcheck to determine if the new program is authorized. Step 1102 mayprevent the receiving device from executing programs which were notcreated by the manufacturer of the receiving device. Each program may beencoded with a combination of a random number and a key stored on thedevice which is to execute the program. A download file header includedwith the program may include the random number and a separate encodingchallenge. To perform the authorization check, the MFED may send theencoding challenge to the receiving device.

If the receiving device is able to decode the encoding challenge, theprogram is considered authorized and the download may proceed to step1106. If the receiving device cannot decode the encoding challenge, atstep 1108 the MFED may send the encoding challenge up to three timesbefore stopping at step 1110.

At step 1106 the MFED attempts to send the new program and the downloadfile header. At step 1112, the MFED determines if the receiving devicehas successfully downloaded the new program. If so, the program updateis finished at step 1114. If the download is unsuccessful, at step 1116the MFED may attempt to send the program up to three times beforestopping at step 1110.

To update an application program on a receiving device, process 1100 maytypically be performed twice. First, the MFED may send the downloaderprogram, because the application program on the receiving device cannotreplace itself. Second, after the downloader program is sent, the MFEDmay send the application program, and the downloader program on thereceiving device may replace the existing application program with theupdated application program.

Referring to FIG. 12, depicted is an exemplary method 1200 which areceiving device may perform to download software from an MFED. Thereceiving device may begin at step 1202 by executing the boot loaderprogram. At step 1204, the boot loader may determine if the receivingdevice contains an application program to execute. The boot loader mayperform this step by checking for an application “magic number” whichsignifies the existence of an application program. If no applicationprogram is available, the boot loader may determine at step 1206 if thereceiving device contains a downloader program to execute. The bootloader may likewise perform this step by checking for a downloader“magic number” which signifies the existence of a downloader program. Ifthe receiving device contains neither an application program nor adownloader, method 1200 may stop at step 1208.

If an application program is located at step 1204, the boot loader mayexecute the application program at step 1210. The application programmay cause the receiving device to perform its normal functions. Forexample, a transmit controller may process user input for controllingthe model vehicle. A telemetry sensor may capture and transmit telemetrydata.

The receiving device may continue to execute the application program toperform its normal functions until it receives a message from an MFEDinstructing it to download a program. Then, at step 1212, the receivingdevice may perform the authorization check, working in conjunction withthe MFED. The receiving device may attempt to decode the securitychallenge and inform the MFED whether it was able to do so. If thereceiving device is unable to decode the security challenge, it informsthe MFED at step 1214.

If the receiving device is able to download the security challenge, thereceiving device determines whether the program the MFED is attemptingto send is a downloader program. If the program is not a downloaderprogram, it is an application program, and an application program cannotdownload another application program. Therefore, at step 1216, theapplication program erases the application magic number and the processreturns to step 1202. Because the application magic number was erased,the boot loader will not execute the application at step 1204.

If the program is a downloader program, at step 1218 the receivingdevice downloads the downloader program and the associated download fileheader. The receiving device may decode the downloader program using therandom number stored in the file header and the key stored on thereceiving device. At step 1220, if the update was successful theapplication program may return to executing the application at step1210. The MFED may then typically attempt to send the updatedapplication program, causing the application magic number to be erasedat step 1216 and the recently downloaded downloader program to beexecuted at step 1222. If the update was not successful the receivingdevice may instruct the MFED about the failure at step 1214.

At step 1222, the boot loader may execute the downloader program. Thedownloader program may download an application program similarly to howan application program downloads a downloader program. However, thedownloader program may simply wait for an MFED to send an applicationprogram at step 1222, rather than performing the normal functions of thereceiving device. At step 1224, the downloader program may determine ifthe download from the MFED is authorized, and at step 1226 thedownloader program may determine if the MFED is attempting to send anapplication program. Similar to an application program, a downloaderprogram may be unable to replace itself with a second downloaderprogram. If the download is not authorized or MFED is attempting to senda downloader program, at step 1228 the downloader program may notify theMFED of the failure and return to executing the downloader program atstep 1222.

At step 1230 the downloader program may download the application programand the associated download file header. The downloader program maydecode the application program using the random number in the downloadfile header and the key stored on the receiving device. At step 1232,the downloader program may determine if the update was successful. Ifthe update was not successful, the downloader program may instruct theMFED about the failure at step 1228 and return to executing thedownloader at step 1222. If the update was successful, the downloaderprogram may execute the boot loader at step 1202. Because an applicationprogram was downloaded, the boot loader may execute the application atstep 1210.

User documentation for an exemplary MFED application is reproducedbelow.

Model Memory

Each time the Traxxas Traxxas-Link is bound to a new receiver, thatreceiver and its settings is stored in the Model Memory. Traxxas' latestmodels include identification data in the receiver, enabling yourTraxxas Link to automatically recognize which model the receiver isinstalled in. Traxxas Link will automatically store settings for up to30 models in Model Memory. When you switch a model on, Traxxas Link willautomatically recognize the receiver and return to the settings lastused with that receiver/model.

Telemetry Configuration

The Telemetry Configuration screen shows the sensors that are installedon your model. Touch Sync Now with your model switched on and linked tothe transmitter, and any Installed sensors will appear in the SlotPosition column. Tap a sensor to change its name; for example, you maywish to name the Temperature sensor “Motor Temp” or “Speed ControlTemp.”

Channel Setup

Traxxas Link's Channel Setup menu allows you to select the each of the 5available channels and set the Sub-Trim, Left Endpoint and RightEndpoint for each channel. You can also “reverse” the channel (forexample, if moving the transmitter's steering wheel left causes thevehicle to steer to the right, the steering servo must be reversed torestore proper control function.) Simply touch the button for thechannel you wish to set up, then move the sliders or tap the +/− iconsto alter the settings. After you select a channel to adjust, tap the “?”icon to learn more about the settings.

Channel 3/4/5 Setup

The Channel Setup screen allows quick and easy adjustments to theservo's Sub-Trim and Endpoints; touch the headings below to expand andlearn more.

Sub-Trim

The Sub-Trim function is used to precisely set the neutral point of theservo.

Left Endpoint/Right Endpoint

The limit of the servo's travel range (or its “end point”) can be setindependently for left and right travel. This allows you to fine-tunethe servo settings to prevent binding caused by the servo moving alinkage or component farther than its mechanical limit.

Normal/Reversed

Switch from Normal to Reversed (or vice versa) if the servo moves in theopposite direction of your intended command.

Reset Factory Defaults

Tap to return the Sub-trim and Endpoint settings to the original factorysettings for the selected model.

Dashboard

The Dashboard is where you can view all the vital functions of yourvehicle as you drive—just like the dashboard of a full-size car. Butunlike that dashboard, the [Traxxas BART] dashboard can be configured tosuit your preferences for data, display style, warning thresholds, andmore.

Available Gauges:

Temperature

[Traxxas BART]'s telemetry system monitors motor or engine temperature.With the Dashboard, you can set a maximum temperature value, and[Traxxas BART] will alert you when the temperature exceeds the limit.The Model Data Base the is loaded into the [Traxxas BART] applicationprovides factory recommended warning level settings that areautomatically set for the specific model vehicle you are connected to.The User has the ability to override these warning levels to hispreference.

Mph

[Traxxas BART] does more than just show you your vehicle's speed; itsaves your maximum speed, and can be set with a warning threshold.exceedthe speed limit, and [Traxxas BART]'s alarm will let you know you'regoing too fast! Using the advanced grid gauge, you can set the gauge toremember the max, min, or average value of speed.

Rpm

Revolutions Per Minute—how fast is your motor or engine spinning? Thisvital information allows you to monitor performance, see the effect ofgearing changes, and make sure you're achieving peak power. You can evenset your own redline, and [Traxxas BART] will alert you if you rev toohigh.

Screen Shots and Recording

Save a still image of the Dashboard, or record the dashboard display ofyour run in real time and play it back. [Traxxas BART] allows you toname and save recordings. Even if you aren't recording, you can replaythe last minute of dashboard data by selecting .Capture.

Customizing the Dashboard

Tap the dashboard to display Wrench icons (to edit gauges), Reset icons(to reset gauges) and + icons (to add gauges to the dashboard). You willalso see .Select Dashboard., .Reset Dashboard., .Record., and .InstantReplay. buttons.

Tap .Select Dashboard. choose the Gauge Cluster Dashboard or GridDashboard designs.

To edit a gauge, touch the Wrench icon over the gauge; to add a gauge tothe dashboard, touch the + symbol where you wish the gauge to appear.

To reset a gauge's saved minimum or maximum values, touch the reseticon.

Drive Effects

The Drive Effects controls allow you to customize “feel” of your model'ssteering, throttle, and brake. The items below can be adjusted easily bymoving a slider or tapping the “<” and “>” controls. You can also assignany of the Drive Effects controls to the Multi-Function Knob for easyadjustment on the fly.

Steering Sensitivity

The Steering Sensitivity control (also known as Steering Exponential, orExpo) adjusts the responsiveness of the model's steering servo. When setfor “zero,” the steering servo's travel (and with it, the steeringmotion of the model's front wheels) corresponds precisely with thesteering wheel. As the Sensitivity value is increased, the steeringbecomes less responsive near neutral, with increasing sensitivity as theservo nears the limits of its travel range. The farther you turn theknob, the more pronounced the change in steering servo movement will be.

Throttle Sensitivity

Throttle Sensitivity (Throttle Exponential) works the same way asSteering Sensitivity, but effects the responsiveness of the throttleservo or electronic speed control. Only forward throttle is affected;brake/reverse travel remains linear regardless of the ThrottleSensitivity setting.

Steering %

Steering %, also known as Dual Rate, controls the amount (percentage) ofservo travel applied to steering. Setting the value to 100% will providefull steering throw; by reducing the value, steering throw will bereduced. Steering % is used to adjust steering throw to match the needsof your track or driving conditions; to set the maximum left and righttravel limits of the steering servo, use the End Point settings in theGarage.

Braking %

Braking %/Dual Rate functions controls the amount of brake travelapplied by the servo in a nitro-powered model. Electric models do nothave a servo-operated brake, but the Braking Percentage function stilloperates the same way in electric models. Setting Braking % to 100%delivers maximum braking capability; reducing the value reduces brakingforce (note: setting Braking % to zero will eliminate all brakingaction).

Throttle Trim

Throttle Trim allows you to adjust the throttle's neutral position toprevent unwanted brake drag or throttle application when the transmittertrigger is at neutral.

Multi Function Knob

Tap the image of the Multi Function Knob to access the menu of controlsthat may be assigned to the knob. Once assigned, you can easily controlthe function by turning the transmitter's Multi Function Knob.

Edit Gauge

The Edit Gauge screen allows you to modify, name, and remove gauges.Touch the links below for more information.

Remove Gauge

Tap .Remove Gauge. to delete a gauge face from the dashboard. The gaugewill appear as a .blank. until a new gauge face is assigned.

Set Warning Level

Warning Levels allow you to program BART to sound an alarm when thegauge exceeds a certain value (for example, you could set an alarm if acertain rpm is exceeded). If the gauge's readout exceeds the warninglevel, BART will sound an alarm and/or vibrate depending on thepreference you have set.

Change Display Name

Tapping Change Display Name will open a dialog box where you may input anew name for the gauge.

Updates

The latest updates for the Traxxas Link software are located here. Touchan update to a view its description. To load the updates, touch UpdateFirmware. Once you begin the update, do not switch off the transmitteror your mobile device.

Garage

The Garage is where you can modify the settings for your model,including Training Mode settings, gear ratio, tire type, battery type,and more. The Traxxas Link app is pre-loaded with the factory settingsfor all Traxxas models. These settings can be changed, then saved as newprofiles that you name. If you wish to return to the factory settings,they can be reloaded at any time. You can access the following screensfrom the Garage. Touch the headings for more information:

Model Select

Traxxas Link automatically recognizes the model you have switched on. Ifyou have moved your receiver to another vehicle, or have purchased a newreceiver that is not already associated with a vehicle, you can use theModel Select screen to assign a new model to the receiver.

Model Setup

In order to provide accurate telemetry data for your model, the TraxxasLink application needs to know the model's gear ratio, tire size,battery type, and other parameters listed in the Model setup screen. Allthe correct parameters for stock Traxxas vehicles are pre-loaded intothe application. If you change the gear ratio, tires, battery type orany of the other parameters, the Model Setup screen is used to input thenew settings.

Telemetry Configuration

The Telemetry Configuration screen lists the sensors installed on yourmodel. The “Sync Now” button will sync the sensors with the Traxxas Linkapplication.

Training Mode

Training Mode allows you to quickly and easily limit the model's topspeed so young, inexperienced, or less-skilled drivers can operate yourmodel more safely and easily.

Model History

A complete list of all the models the TQi transmitter has been bound tocan be accessed by touching the Model History icon.

Add Gauge—Choose Gauge Face

Slide left to view the gauge designs and tap the design you wish to use.Note that some designs offer a greater range of values; choose the rangethat best suits your vehicle. For example, if your vehicle will exceed30 mph, choose the 0-100 mph gauge face instead of the 0-30 mph gaugeface.

Save Profiles

Tap a Profile to view its settings. To load the Profile, tap LoadProfile.

Multi Function

Tap the Drive Effect you wish to assign to the Multi-Function Knob. Onceselected, it will appear .ghosted. on the Drive Effects screen and mayonly be adjusted by operating the Multi-Function Knob on thetransmitter.

Store Finder

The Store Finder makes it easy to find your local Traxxas Dealer.Traxxas Link may prompt you to allow it to use your location; tap “yes,”and the stores near you will automatically be placed on a map. Or, youmay enter your address manually by selecting Manual Address and fillingin the required information.

Preferences

The Preferences screen lets you customize the BART application to yourliking. The following can be switched on and off:

Record Audio on Dashboard

In addition to recording vehicle data, the Dashboard's recording featurecan record your voice so you can make verbal notes during your run.

Skip First Launch Tutorial

Slide the toggle to OFF if you do not wish [Traxxas BART] to play theintroductory video.

Audio Warnings

Switching Audio off will make BART operate silently. Note that any audioalarms you have programmed will not sound when audio is turned off.

Tactile Feedback

Selecting this option will cause the iPhone to simulate the feel ofphysical buttons by sending a pulse of vibration with each button.press. Note: tactile feedback is not supported by iPod Touch.

Skip Launch Video

Slide the toggle to OFF if you do not wish [Traxxas BART] to play theintroductory video.

Threshold Warnings Enabled

Switching this function to OFF will disable the warning alarms you setusing the Dashboard controls. Your threshold warning setting will not bechanged.

Override Status Bar

Enabling this option will hide the iPod/iPhone's status bar, whichdisplays internet connectivity status, time, and the iPod/iPhone'sbattery status. When the status bar is hidden, the [Traxxas BART]application will use the space to display the transmitter/iPod/iPhoneconnection status, telemetry signal status, and transmitter batterylevel.

Display Timeout

The iPhone/iPod has a timeout feature that automatically dims the screenif no activity is detected. Select .Off. to override the iPhone/iPod'sscreen timeout feature. Select .Not on dashboard. to allow the timeoutfunction to operate normally on all screens except the Dashboard.

Theme

[Traxxas BART] allows you to choose .Light. and .Dark. themes foreasiest viewing. Choose the Light theme for low-light conditions; choosethe Dark theme for use in sunlight or other bright conditions.

Security Code

Model Setup

BART relies on specific information about your model to generateaccurate telemetry data. If you are operating a stock Traxxas model andhave selected that model from the Garage, there is no need to make anychanges to Model Setup. However, if you have made changes to yourmodel's gear ratio, tires, or battery, you will need to input new datain Model Setup or your telemetry results will not be accurate. Be sureto input the correct values for the following:

Spur Gear

This is the large, external gear on the transmission. The numberindicates the number of teeth on the gear.

Pinion Gear

This is the smaller gear that meshes with the spur gear.

Drive Ratio 1/Drive Ratio 2

These numbers represent the gear ratio of the transmission; vehicleswith two-speed transmissions have two drive ratios.

Tires

To accurately calculate speed, BART needs to know the circumference ofthe tires. All of Traxxas' current tires are loaded into the app. Justselect the tires installed on your vehicle.

Battery

Select the battery you use in your vehicle.

Recordings

Replay saved recordings by tapping the name of the recording you wish toplay. The dashboard will display the data collected during therecording, including the total and elapsed time of the recording. TheSort button allows you to arrange the recordings by date (most recentwill appear at the top of the list) or alphabetically (if you've namedyour recordings). To delete a recording, slide from right to left overthe recording title and a Delete button will appear. Tap it to deletethe recording.

Add Gauge

To add a gauge, select what you wish the new gauge to measure: Voltage,Temperature, Speed, or RPM (Tachometer). A variety of gauge designs willappear. Tap the gauge face design you wish to use, and BART will takeyou back to the dashboard with the new gauge in place.

Steering Channel Setup

The Steering Channel Setup screen allows quick and easy adjustments tothe steering servo's Sub-Trim and Endpoints; touch the headings below toexpand and learn more.

Sub-Trim

The Sub-Trim function is used to precisely set the neutral point of thesteering servo in the event that simply setting the trim to “zero” doesnot completely center the servo. When selected,

Sub-Trim allows finer adjustment to the servo output shaft's positionfor precise setting of the neutral point. Always set the Steering Trimto zero before making final adjustment (if required) using Sub-Trim.

Left Endpoint/Right Endpoint

The limit of the servo's travel range (or its “end point”) can be setindependently for left and right travel. This allows you to fine-tunethe servo settings to prevent binding caused by the servo moving thesteering farther than their mechanical limits.

Normal/Reversed

If moving the transmitter's steering wheel left causes the vehicle tosteer to the right (or vice versa), the steering channel'sNormal/Reversed setting is incorrect. If “Reversed” is selected, tap“Normal” to correct the steering function, and vice-versa.

Reset Factory Defaults

Tap to return the Sub-trim and Endpoint settings to the original factorysettings for the selected model.

Throttle Channel Setup

The Steering Channel Setup screen allows quick and easy adjustments tothe steering servo's Sub-Trim and Endpoints; touch the headings below toexpand and learn more.

Sub-Trim

The Sub-Trim function is used to precisely set the neutral point of thethrottle servo in the event that simply setting the trim to “zero” doesnot completely center the servo. When selected, Sub-Trim allows fineradjustment to the servo output shaft's position for precise setting ofthe neutral point. Always set the Throttle Trim to zero before makingfinal adjustment (if required) using Sub-Trim.

Left Endpoint/Right Endpoint

The limit of the throttle servo's travel range (or its “end point”) canbe set independently for throttle and brake travel. This allows you tofine-tune the servo settings to prevent binding caused by the servomoving steering or throttle linkages (in the case of a nitro car)farther than their mechanical limits.

Normal/Reversed

If pulling the transmitter's trigger to activate forward throttleinstead applies the brakes or reverse throttle (or vice versa), thethrottle channel's Normal/Reversed setting is incorrect. If “Reversed”is selected, tap “Normal” to correct the throttle function, andvice-versa.

Reset Factory Defaults

Tap to return the Sub-trim and Endpoint settings to the original factorysettings for the selected model.

Training Mode

Training Mode allows you to quickly and easily reduce the speed of yourmodel so young, inexperienced, or less-skilled drivers can operate itmore easily and safely. To set the Training Mode speed, touch SetupTraining Mode and use the Multi Function Knob to set the desired maximumspeed. You can operate the model while setting the Training Mode speed.When you have set the speed, touch Enter Training Mode and the modelwill not exceed the speed you have set. While Training Mode is active,the green LED on the transmitter will flash slowly. To return to normalfull-throttle operation, touch Disable Training Mode. When thetransmitter is in “normal” mode (Training Mode off), the green LED onthe transmitter will glow green.

Vehicle Model Selection

There are two modes of operation for Vehicle Model Selection—Offline andConnected to Transmitter.

Offline Mode—Edit Model from Model History

Make sure you are NOT connected to a transmitter and tap the model youwish to edit offline; a green .check icon will appear next to it. Thereare two types of models listed in the Model History table—all previouslyconnected models and any new models that the user has created. The lastconnected or edited model will have a green check next to it indicatingthat it is the current active model in memory. Any changes withinVehicle Configuration and Dashboards can be made to the active model inmemory. These will be applied the next time the model connection is madeor the first time newly created models are used. Changes made to ChannelSetup and Drive Effects can be saved to a profile that can be loaded thenext time the current model in memory is connected.

Offline Mode—Create and Edit New Model

You may want to set up for that new vehicle you are planning to get. Todo this, you simply select the desired vehicle from the Model Categorieslist. Once selected, the vehicle will appear (with a green checkmarknext to it) in the Model History List. Any changes within VehicleConfiguration and Dashboards can now be made and these will be appliedthe first time the newly created model is used. Changes made to ChannelSetup and Drive Effects can be saved to a profile that can be loadedwhen the new model in memory is connected.

Connected Mode—Select Active Model

When connected to a transmitter, the Model Memory displays a list of themodels the receiver has been installed in. For example, you may want tomove your receiver from one car to another car model or marine model.When you do this, Model Memory remembers all the models that a receiverwas used in. Model Memory remembers all the settings for each model thatthe receiver was used in. Simply move the receiver to the new model,then select the new vehicle from the Model Categories List and make allof your desired changes to the vehicle settings. You may then move thereceiver back to the original vehicle and select the correct model fromthe Model History List. When connected to a transmitter, the ModelHistory List will only show a list of vehicles that the receiver hasbeen used in.

Choose Model

Slide left to locate the model you wish to select. Touch the model toselect it. The Edit Vehicle Name window will appear. You may type in anew name for the vehicle, or simply touch “Save.” If your transmitterand vehicle are currently “on,” the transmitter will disconnect from thevehicle for a moment while the new model is loaded.

Warning Threshold

Programmable warning levels allow [Traxxas BART] to alert you when alimit you set has been exceeded. For example, if battery voltage dropstoo low, engine temperature is too high, or speed falls below a minimumor exceeds a maximum. To set Warning Levels for analog (dial) gauges,tap the + or . icons to set a warning level, or simply drag theindicator to the position you choose. For digital gauges, tap the valueinto the field using the numeric keypad.

Screen captures of selected portions of the execution of an exemplaryMFED application are shown in FIG. 16A-16AH.

It is noted that the embodiments disclosed are illustrative rather thanlimiting in nature and that a wide range of variations, modifications,changes, and substitutions are contemplated in the foregoing disclosureand, in some instances, some features of the present invention may beemployed without a corresponding use of the other features. Many suchvariations and modifications may be considered desirable by thoseskilled in the art based upon a review of the foregoing description ofvarious embodiments. In particular, an MFED may provide only a subset ofthe previously described features. For example, an MFED may displayoutput but not receive input. An MFED may offer a graphical display ofoperational parameters, but the user may be required to use theparameter user interface of the transmit controller to set theparameters. Alternately, an MFED may be limited to displaying telemetrysensor data, and may have no use in displaying or setting operationalparameters.

Various devices consistent with the preceding disclosure may comprisethe following:

Device 1: A transmit controller having a maximum power parameter, thetransmit controller comprising:

a memory comprising a maximum power parameter;

a control user interface for controlling a model vehicle;

an auxiliary user interface connector for connecting to an auxiliaryuser interface device;

a transmit controller processor configured to:

-   -   receive a throttle instruction from the control user interface,        the throttle instruction identifying a control user interface        acceleration amount;    -   reduce the control user interface acceleration amount        proportionally to the maximum power parameter, producing an        output acceleration amount;    -   transmit an output signal to the model vehicle, the output        signal identifying the output acceleration amount.

Device 2: Device 1, wherein the transmit controller processor is furtherconfigured to reduce the control user interface acceleration amountlinearly proportionally to the maximum power parameter, producing theoutput acceleration amount.

Device 3: Device 1, wherein the transmit controller processor is furtherconfigured to:

receive a maximum power parameter setting from the auxiliary userinterface device; and

change the maximum power parameter to the maximum power parametersetting.

Device 4: Device 1, further comprising a parameter user interface,wherein the transmit controller processor is further configured to:

receive a maximum power parameter setting from the parameter userinterface; and

change the maximum power parameter to the maximum power parametersetting.

Device 5: Device 1, further comprising a parameter user interface,wherein the transmit controller processor is further configured totransmit the maximum power parameter setting to the auxiliary userinterface device.

Device 6: An auxiliary user interface device configured to:

receive a maximum power setting from a transmit controller; and

graphically display the maximum power setting.

Device 7: An auxiliary user interface device configured to:

receive a maximum power setting from a graphical user interface userinput; and

transmit the maximum power setting to a transmit controller.

Device 8: A transmit controller capable of automatic configuration, thetransmit controller comprising:

a memory comprising one or more operational parameters;

a control user interface for controlling a model vehicle;

an auxiliary user interface connector for connecting to an auxiliaryuser interface device;

a transmit controller processor configured to:

-   -   receive a vehicle identifier from a model vehicle receiver;    -   transmit the vehicle identifier to the auxiliary user interface        device;    -   receive one or more operational parameter settings from the        auxiliary user interface device in response to the transmission        of the vehicle identifier;    -   change the one or more operational parameters to the one or more        operational parameter settings;    -   receive a control instruction from the control user interface;    -   determine an output signal based on the control instruction and        the one or more operational parameters; and    -   transmit the output signal to the model vehicle.

Device 9: An auxiliary user interface device configured to:

receive a vehicle identifier from a transmit controller;

identify one or more operational parameter settings associated with thevehicle identifier in a vehicle database; and

transmit the one or more operational parameter settings to the transmitcontroller.

Device 10: An auxiliary user interface device configured to:

store one or more operational parameter settings;

transmit the one or more operational parameter settings to a networkaddress at a server; and

send an electronic mail message comprising the network address.

Device 11: Device 10, further configured to open an electronic mailapplication to a draft of the electronic mail message, the draft of theelectronic mail message comprising the network address.

Device 12: An auxiliary user interface device configured to:

receive an electronic mail message comprising the network address of oneor more operational parameter settings;

retrieve the one or more operational parameter settings from the networkaddress; and

store the one or more operational parameter settings.

Device 13: An auxiliary user interface device configured to:

receive a sensor identifier from a transmit controller, the sensoridentifier identifying a telemetry sensor;

determine, from the sensor identifier, a graphical user interfacecomponent for displaying telemetry data from the telemetry sensor;

receive telemetry data from the telemetry sensor;

display the graphical user interface component, the graphical userinterface component comprising the telemetry data.

Device 14: Device 13, wherein the auxiliary user interface device beingconfigured to determine, from the sensor identifier, the graphical userinterface component comprises the auxiliary user interface devicefurther configured to:

determine, from the sensor identifier, a plurality of graphical userinterface components for displaying telemetry data from the telemetrysensor;

display the plurality of graphical user interface components; and

receive a user input identifying the graphical user interface component.

Device 15: An auxiliary user interface device for creating a dashboardvideo, the auxiliary user interface device configured to:

receive a telemetry data stream from a transmit controller, thetelemetry data stream comprising the values of one or more telemetrydata items over a time period;

record the telemetry data stream; and

subsequent to the recording of the telemetry data stream, create agraphical representation of the telemetry data stream.

Device 16: Device 15, wherein the graphical representation of thetelemetry data stream comprises a video.

Device 17: Device 15, wherein the graphical representation of thetelemetry data stream comprises a plurality of graphical user interfacecomponents, each of the plurality of graphical user interface componentsdisplaying the values of at least one of the one or more telemetry dataitems over the time period.

Device 18: Device 17, wherein the graphical user interface componentsare user selected.

Device 19: An auxiliary user interface device for replaying telemetrydata, the auxiliary user interface device configured to:

receive a telemetry data stream from a transmit controller, thetelemetry data stream comprising the values of one or more telemetrydata items over a time period;

record the most recent values of the telemetry data items in a circularbuffer;

receive an instruction to display the contents of the circular buffer;

in response to receiving the instruction, record the contents of thecircular buffer separately from the circular buffer; and

display a graphical representation of the contents of the circularbuffer.

Device 20: Device 19, wherein the graphical representation of thecontents of the circular buffer comprises a video.

Device 21: Device 19, wherein the graphical representation of thetelemetry data stream comprises a plurality of graphical user interfacecomponents, each of the plurality of graphical user interface componentsdisplaying the values recorded in the circular buffer of at least one ofthe one or more telemetry data items.

Device 22: Device 21, wherein the graphical user interface componentsare user selected.

Device 23: An auxiliary user interface device for updating anapplication program of a receiving device, the auxiliary user interfacedevice configured to:

receive an updated application program from a data network; and

transmit the updated application program to a model vehicle transmitcontroller.

Device 24: Device 23, wherein the model vehicle transmit controller isthe receiving device.

Device 25: Device 23, wherein the model vehicle transmit controller isconfigured to transmit the updated application program to the receivingdevice.

We claim:
 1. A transmit controller capable of automatic configuration, the transmit controller comprising: a memory comprising one or more operational parameters effecting a control instruction for controlling movement; a control user interface for remotely controlling movement of a model vehicle; an auxiliary user interface connector for connecting to an auxiliary user interface device, the auxiliary user interface device comprising a processor to automatically configure the transmit controller; a transmit controller processor comprising a configuration to: receive a vehicle identifier from a model vehicle receiver; transmit the vehicle identifier to the auxiliary user interface device; receive one or more operational parameter settings from the auxiliary user interface device in response to the transmission of the vehicle identifier; change the one or more operational parameters to the one or more operational parameter settings; receive the control instruction from the control user interface; determine an output signal based on the control instruction and the changed one or more operational parameters; and transmit the output signal remotely to the model vehicle to thereby control the movement of the model vehicle.
 2. The auxiliary user interface device of claim 1, wherein the one or more operational parameter settings comprises at least one of a steering expo setting and a brake percentage setting.
 3. The auxiliary user interface device of claim 1, wherein the one or more operational parameter settings comprises at least one of an end point setting and a servo reversing setting.
 4. The transmit controller of claim 1, further comprising: the auxiliary user interface device for automatically configuring a transmit controller, the auxiliary user interface device comprising a configuration to: receive a vehicle identifier from a transmit controller; identify one or more operational parameter settings associated with the vehicle identifier in a vehicle database; and transmit the one or more operational parameter settings to the transmit controller.
 5. The auxiliary user interface device of claim 4, wherein the one or more operational parameter settings comprises at least one of a steering expo setting and a brake percentage setting.
 6. The auxiliary user interface device of claim 4, wherein the one or more operational parameter settings comprises at least one of an end point setting and a servo reversing setting.
 7. The transmit controller of claim 1, further comprising: the auxiliary user interface device transmitting operational parameter settings, the auxiliary user interface device comprising a configuration to: store one or more operational parameter settings; transmit the one or more operational parameter settings to a network address at a server; and send an electronic mail message comprising the network address.
 8. The auxiliary user interface device of claim 7, wherein the one or more operational parameter settings comprises at least one of a model vehicle acceleration configuration, a model vehicle steering configuration, a model vehicle braking configuration.
 9. The auxiliary user interface device of claim 7, wherein the configuration is further to open an electronic mail application to a draft of the electronic mail message, the draft of the electronic mail message comprising the network address.
 10. The transmit controller of claim 1, further comprising: the auxiliary user interface device receiving operational parameter settings, the auxiliary user interface device comprising a configuration to: receive an electronic mail message comprising a network address of a network location associated with the one or more operational parameter settings; retrieve the one or more operational parameter settings from the network address location; and store the one or more operational parameter settings.
 11. The auxiliary user interface device of claim 10, wherein the one or more operational parameter settings comprises at least one of a model vehicle acceleration configuration, a model vehicle steering configuration, a model vehicle braking configuration.
 12. The auxiliary user interface device of claim 10, wherein the configuration is further to: recognize the network address as a network location of one or more operational parameter settings; and in response to recognizing the network address, launch an application for operating a model vehicle.
 13. The auxiliary user interface device of claim 10, wherein the configuration is further to configure the auxiliary user interface device to use at least some of the one or more operational parameter settings.
 14. The auxiliary user interface device of claim 10, wherein the configuration is further to configure a transmit controller to use at least some of the one or more operational parameter settings.
 15. The transmit controller of claim 1, further comprising: the auxiliary user interface device updating an application program of a receiving device, the auxiliary user interface device comprising a configuration to: receive an updated application program from a data network; and transmit the updated application program to a model vehicle transmit controller.
 16. The auxiliary user interface device of claim 15, wherein the model vehicle transmit controller is the receiving device.
 17. The auxiliary user interface device of claim 15, wherein the model vehicle transmit controller is configured to transmit the updated application program to the receiving device.
 18. The auxiliary user interface device of claim 15, wherein the configuration is further to communicate with the receiving device through the model vehicle transmit controller.
 19. The auxiliary user interface device of claim 15, wherein the configuration is further to send an encoding challenge to the receiving device.
 20. The auxiliary user interface device of claim 15, wherein the configuration is further to transmit a downloader program to the model vehicle transmit controller prior to transmitting the updated application program to the model vehicle transmit controller. 